home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
TeX 1995 July
/
TeX CD-ROM July 1995 (Disc 1)(Walnut Creek)(1995).ISO
/
tex-k
/
tex-k-archive.past
/
tex-k-archive.gz
/
tex-k-archive
/
000411_kb@cs.umb.edu_Sun Mar 20 00:42:30 1994.msg
< prev
next >
Wrap
Internet Message Format
|
1994-10-11
|
1KB
Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA02586
(5.65c/IDA-1.4.4 for <tex-k-exp@cs.umb.edu>); Sun, 20 Mar 1994 08:31:02 -0500
Received: by terminus.cs.umb.edu id AA25784
(5.65c/IDA-1.4.4 for tex-k); Sun, 20 Mar 1994 05:42:30 -0500
Date: Sun, 20 Mar 1994 05:42:30 -0500
From: "K. Berry" <kb@cs.umb.edu>
Message-Id: <199403201042.AA25784@terminus.cs.umb.edu>
To: tex-k@cs.umb.edu
Subject: db vs. filesys searching
About this database searching stuff.
I can understand not wanting to search one big overloaded font server.
But maybe I didn't make myself clear: the idea is that only files that
(1) are *not* found in the database and
(2) must exist
are looked for on the filesystem. At least 99% of all TeX/dvips/xdvi
runs fall into that category. And certainly startup time (which almost
always involves only existing files) should not be generally increased.
Anyway, this db stuff has only existed for a few months. What have you
been doing for the last umpteen *years*? Just living with lengthy
searches? I'm guessing you're not trying to do subdirectory searching or
anything, just having one (or a few) big directories with all the files?
All that said, I don't mind providing a way to turn off filesystem
searches; I just made a leading `%%' in a path spec mean this. Seemed
simpler than having a magic character at both the beginning and end.